Method and system for data session establishment

ABSTRACT

A method and system for data session establishment from a mobile device in a multiple networks scenario, the method including, checking whether an identifier for an first network is on a blacklist on the mobile device; if the first network identifier is not on the blacklist, attempting to establish a data connection with the first network; and if the first network identifier is on the blacklist, establishing a data connection with a second network. The method and system for data session establishment include deriving and maintaining the blacklist.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/474,968, filed Sep. 2, 2014, which is a continuation of U.S.patent application Ser. No. 12/829,530, filed Jul. 2, 2010, and nowissued as U.S. Pat. No. 8,843,112, the entire contents of all of whichare incorporated herein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates to mobile devices and in particular tothe establishment of data sessions from the mobile devices.

BACKGROUND

A Code Division Multiple Access (CDMA) 1×/EVDO hybrid access terminal(mobile device) is a device which operates in a hybrid fashion thatsupports both CDMA 1× and EVDO radio access technologies (RATs). EVDOstands for Evolution Data Only or Data Optimized and, as suggested bythis, is a data only system. EVDO is alternatively known as High RatePacket Data (HRPD). One advantage of an EVDO system is that it allows ahigher transfer rate for data. EVDO networks are also useful to carriersto free CDMA 1× system voice capacity by removing data traffic from theCDMA 1× system.

A mobile device operating in a CDMA 1×/EVDO hybrid mode will firstacquire either an EVDO network or a CDMA 1× network, and once thisnetwork has been acquired and it is in an idle state the mobile devicewill then try to acquire an associated 1× network or an associated EVDOnetwork respectively.

In order to acquire the EVDO system, an access network (AN)authentication must occur through an A12 interface. A12 is the interfacethat carries signaling information related to access authenticationbetween the Session Controls/Mobility Management (SC/MM) functions inthe AN and the AN-AAA (Access Network-Authentication, Authorization andAccounting Entity). AN authentication uses a Challenge-HandshakeAuthentication Protocol (CHAP) to authenticate a mobile device. ANauthentication occurs upon the mobile device first attempting to accessthe access network and establish an initial EVDO session and is repeatedafter a session timeout or the access network fails to reach the mobiledevice after a keep alive timer expires. A12 interfaces are described inthe Third Generation Partnership Project 2 (3GPP2) A.S0008specification, the contents of which are incorporated herein byreference.

If AN authentication fails, the mobile device will periodically attemptto connect with the EVDO network to establish an EVDO session. Therepetition of connection attempts wastes network resources and batterylife on the device since the authentication failure likely signalsfuture authentication failures. In addition, the repeated attempts toauthenticate AN may delay data session setup on a CDMA 1× network,potentially resulting in a poor user experience.

Similarly, for devices that support a hybrid mode of other RATsoperating under multiple networks, authentication on a first network mayfail. Repetition of connection attempts to that network waste resources.For example, a connection to a Long Term Evolution (LTE) network may beattempted, and may fail. Further connection attempts to the LTE networkmay waste resources and may delay data session setup on networks ofdifferent RATs found over the air.

BRIEF DESCRIPTION

The present disclosure will be better understood with reference to thedrawings in which:

FIG. 1 is a data flow diagram showing EVDO access network authenticationof a mobile device;

FIG. 2 is a flow diagram showing a process for network connection in amultiple networks scenario;

FIG. 3 is a flow diagram showing a process for data sessionestablishment over a hybrid coverage of EVDO and CDMA 1×;

FIG. 4 is an exemplary blacklist table;

FIG. 5 is a flow diagram showing a process for clearing entries from ablacklist;

FIG. 6 is a block diagram showing exemplary hybrid CDMA 1×/EVDO network;and

FIG. 7 is a block diagram of an exemplary mobile device.

DETAILED DESCRIPTION

The present disclosure provides a method for data session establishmentfrom a mobile device comprising checking whether an identifier for afirst network is on a blacklist on the mobile device; if the firstnetwork identifier is not on the blacklist, attempting to establish adata connection with the first network; and if the first networkidentifier is on the blacklist, establishing a data connection with asecond network.

The present disclosure further provides a mobile device configured fordata session establishment with a network comprising: a communicationssubsystem; and a processor, wherein the mobile device is configured to:check whether an identifier for an first network is on a blacklist onthe mobile device; if the first network identifier is not on theblacklist, attempt to establish a data

The present disclosure is described below with regard to a CDMA 1× andEVDO. This is however not meant to be limiting and the methods andsystems described herein could be equally applied to other radio accesstechnologies (RATs). Such other radio access technologies include, butare not limited to, Evolved Universal Mobile Telecommunications SystemTerrestrial Radio Access Network (EUTRAN, also referred as Long TermEvolution or LTE), UMTS Terrestrial Radio Access Network (UTRAN), GSMEDGE Radio Access Network (GERAN), among others. The use of CDMA 1× andEVDO below is therefore only for illustrative purposes.

Reference is now made to FIG. 1. FIG. 1 shows EVDO access networkauthentication. In FIG. 1, a mobile device 110 communicates with anAccess Network (AN) 112, which in turn communicates with a VisitedAccess Network AAA 114. Visited Access Network AAA 114 communicates witha Home Access Network AAA 116.

A mobile device 110 communicates with Access Network 112 for sessionestablishment, as seen by arrow 120. A point-to-point protocol (PPP) andlink control protocol (LCP) negotiation then occur between the mobiledevice 110 and the AN 112, as seen by arrow 130.

After the PPP and LCP negotiations, AN 112 sends a CHAP challenge 140 tomobile device 110. In response, mobile device 110 sends CHAP response142 back to AN 112. The response 142 is based on the A12 CHAP identifierand includes the A12 network access identifier (NAI) and the CHAP accessauthentication password.

AN 112 then sends visited access network AAA 114 an A12 access request150. A12 access request 150 includes the challenge and response.

Visited access network AAA 114 then uses a network access identifier toforward message 152 to the proper home AN-AAA server 116.

Home AN-AAA 116 validates the CHAP response and responds with anauthorization response as shown by message 160. The visited accessnetwork AAA 114 forwards the response to AN 112, as shown by message162.

The AN 112 then informs the mobile device 110 of the A12 authenticationresults, as seen by message 164. As defined in 3GPP2 A.S0008 the resultmay be A12 access-accept or A12 access-reject.

The access network authentication may result in rejection if, forexample, the mobile device is not provisioned by the network to allowEVDO access. For example, a mobile device may be in a roaming networkwith no home network agreement. Other reasons for authentication failurewill be known to those in the art.

Always on mobile devices generally desire the establishment of a datasession at the earliest opportunity. The EVDO access networkauthentication typically coincides with EVDO session set up, andprecedes data session setup. Repeated failed attempts at authenticatingAN in this scenario delays data session setup, potentially resulting ina poor user experience. For example, the delay in the data session setupmay be perceived as a stall in acquiring data services at the mobiledevice. Further, the repeated attempts to authenticate AN may result inpossible battery life impacts since vendors may deploy some sort of EVDOsession recovery, which if network provision and conditions do notchange, will always fail when attempting AN authentication. In addition,over the air resources may be wasted. Device should therefore find analternate way to establish a data session and avoid unnecessary repeatedattempts to authenticate AN.

When authentication fails with a network associated with a particularRAT, it may in some scenarios be advantageous to attempt a dataconnection on a network of a different RAT instead of a network of thesame RAT. In an EVDO+EUTRAN (LTE)+UTRAN (UMTS)+GERAN (GSM)+CDMA 1×coverage for example, if the terminal fails to authenticate with theEVDO network, it may fall back to an attempt to attach with the EUTRANor UTRAN or GERAN network or authenticate with the CDMA 1× network. Aswill be appreciated, additional EVDO networks discovered over the airmay share the same authentication entity as the EVDO network initiallydiscovered. The probability of failing authentication is higher whenre-trying authentication with EVDO networks that may share the sameauthentication entity than attempting a data connection on a networkwith an alternative radio access technology (RAT) which has a differentauthentication entity. Moreover, the retry interval mandated by aparticular RAT may further delay data session setup.

Thus, if failing data authentication on a network of one RAT, a furtherattempt can be made on a second network of a different RAT that may beassociated with the original network, but has a different authenticationentity. The first network and the second network may belong to the samewireless carrier, or they belong to different wireless carriers thatthey may have roaming agreements between each other. As a result, thetwo networks of different RATs may have some form of association betweeneach other. For EVDO and CDMA 1× the association is through thePreferred Roaming List or Extended Preferred Roaming List as describedin 3GPP2 C.S0016, or through the use of broadcast message “AlternativeTechnologies Information Message” as described in 3GPP2 C.S0005-E. EVDOis authenticated by AN-AAA while CDMA 1× data is authenticated by an AAAserver, as described above. For EUTRAN and EVDO, the association isthrough broadcast messages such as SystemInformationBlockType8 of 3GPPTS 36.331 and E-UTRAN Neighbor List Record of 3GPP2 C.S0087, thecontents of which are incorporated herein by reference. EUTRAN and EVDOare authenticated by home subscriber server (HSS) and AN-AAArespectively. For EUTRAN/UTRAN/GERAN, these may have differentauthentication entities but be associated by public land mobile network(PLMN). In addition, networks of different RATs may also be associatedthrough the use of a provisioning message “multi-mode system selection(MMSS) system Priority List (MSPL)”, as described in 3GPP2 C.S0016-D.Other ways of associating networks of different RATs will be known tothose in the art.

The association between the first network and the second network may, insome cases, be that the first and second networks utilize differentauthentication entities, thus providing a higher probability ofsuccessful data connection on the second network if authentication failson the first network. In other embodiments, the first network and thesecond network may be related by data speed. Thus the first network maybe a higher speed data network and the second network may have a lowerspeed data connection. For example, the device may try to connect withan EUTRAN network first and then fall back to an UTRAN or GERAN network,or may attempt to connect with an EVDO network first and fall back to aCDMA 1× network to connect data.

Further, in one embodiment a first network with a higher data rate maybe an overlay of the second network, the second network having a lowerdata rate and larger footprint than the first network. For example, thedevice may try to connect with an EUTRAN network first which has asmaller footprint and then fall back to an EVDO network which has alarger footprint due to the fact that it was introduced for a longertime.

The networks may utilize messages to define relationships betweenthemselves. Such messages may include, for example, the broadcast orprovisioning messages described above. In other cases, networks mayutilize associations such as the PLMN. In further cases, networks mayutilize Preferred Roaming List or Extended Preferred Roaming List forassociations.

As will be appreciated by those in the art, a list may be maintained ofthe loss indication failures encountered. A general case is describedwith regards to FIG. 2.

Specifically, reference is now made to FIG. 2, which shows a processdiagram for network connection in a multiple networks scenario.

Specifically, the process of FIG. 2 starts at block 200 and proceeds toblock 210 in which the first network to connect to and authenticate withis determined. The determination of block 210 may be predefined. Forexample, a mobile device may wish to connect to an EUTRAN network first.Alternatively, the mobile device may prefer to connect to an EVDOnetwork, for example.

The first network of block 210 may be any of the networks describedabove, such as EUTRAN, UTRAN, GERAN, EVDO, and CDMA 1×, among others.The first network may also be any other network the mobile device wishesto connect to.

From block 210, the process proceeds to block 212 in which adetermination is made of whether the first network is on a blacklist. Ifyes, the process proceeds to block 222 in which a data connection isestablished with a second network. As will be appreciated by those inthe art, the second network may be any network related to the firstnetwork, and examples include an EVDO or UTRAN or GERAN or CDMA 1× asthe second network when the first network is EUTRAN, CDMA 1× for thesecond network when the first network is EVDO, among other examples.

The connection in block 222 may also include checks to ensure the secondnetwork is not on a blacklist (not shown).

From block 222 the process proceeds to block 230 and ends.

If, in block 212, it is determined that the first network is not on ablacklist, the process proceeds to block 220 in which a connectionattempt is made to the first network. The process then proceeds to block224 in which a check is made to determine whether the connection wasauthenticated.

From block 224, if the connection was not rejected the process proceedsto block 230 and ends. If the connection was rejected, the processproceeds from block 224 to block 226 in which the first network isplaced on the blacklist. The process then proceeds to block 222 toconnect on the second network as described above.

The process of FIG. 2 may be illustrated with regard to a hybridEVDO/CDMA 1× coverage. Reference is now made to FIG. 3.

The process of FIG. 3 starts at block 300 and proceeds to block 310 inwhich the mobile determines which EVDO network to acquire andauthenticate.

The process then proceeds to 312 in which a check is made to determinewhether the EVDO network acquired is on a blacklist. The blacklist isexplained in more detail below.

If, in block 312, it is determined that the EVDO network is on ablacklist, the process proceeds to block 322 in which the mobile decidesto authenticate a data session on a related CDMA 1× network. The processthen proceeds to block 330 and ends. As will be appreciated by those inthe art, if the EVDO network is on the blacklist, AN authentication withthe EVDO network is likely to fail and thus an attempt to connect withthe EVDO network is avoided and data is established over the relatedCDMA 1× network instead.

Conversely, if in block 312 the EVDO network is not on a blacklist, theprocess proceeds to block 320 in which the mobile attempts to setup anEVDO session and authenticate AN with the EVDO network.

From block 320 the process proceeds to block 324 in which a check ismade to determine whether the AN authentication was accepted orrejected. If the AN authentication was rejected the process proceeds toblock 326 in which the EVDO network is added to the blacklist and theprocess then proceeds to block 322 to connect to the related CDMA 1×network for the data session, as described above.

If, in block 324 it is determined that A12 authentication was successfulthe process proceeds to 330 and ends.

Based on FIG. 3 above, identifiers for EVDO networks are maintained on ablacklist for a time in order to avoid multiple attempts at establishingan EVDO session after an AN authentication rejection.

In a further embodiment, the addition of an EVDO network to theblacklist in block 326 may also involve the addition of associated EVDOnetworks to the blacklist. In particular, an EVDO network on aparticular channel (e.g. channel x) can broadcast the existence of otherEVDO networks (e.g. EVDO networks on channel y and z) through aSectorParameters message as described in 3GPP2 C.S0024. This can, forexample use the ChannelCount/Channel field andNeighborChannelIncluded/NeighborChannel field in the SectorParametersmessage. The information can thus be broadcast on a broadcast channel ofthe EVDO network.

In most of cases, EVDO networks on channel y and z from the exampleabove will typically belong to the same carrier as EVDO network onchannel x. The other EVDO networks will thus likely have similarauthentication requirements.

If the device has attempted AN authentication on EVDO network on channelx and failed, in one embodiment the mobile device can proactively avoidscanning to and attempting AN authentication on EVDO networks on channely and z because there is a high probability that AN authentication willalso fail. This can be done through the addition of identifiers of EVDOnetwork on channel x, but also identifiers of EVDO networks on channel yand channel z, to the blacklist in block 326. The addition ofidentifiers of EVDO networks on channel y and channel z at the same timeidentifiers of EVDO network on channel x is added will prevent thesystem from attempting to connect to these EVDO networks in blocks 310and 320, thereby saving battery and network resources and potentiallyleading to a faster establishment of a data session on the CDMA 1×network.

As will be appreciated, the use of three channels above is only meantfor illustrative purposes, and the system could have any number of EVDOnetworks.

The addition of identifiers of associated networks of the same RAT tothe blacklist could also be applied to any of the RATs described above.Identifiers of associated networks of the same RAT could be derived frominformation broadcasted on a broadcast channel. Other ways of addingassociated networks of the same RAT to the blacklist would be known tothose in the art.

Reference is now made to FIG. 4. FIG. 4 shows an exemplary blacklistthat may be maintained by a mobile device. In particular, a blacklist ofFIG. 4 shows two fields, namely the identifier field 410 and a timestampfield 420.

The identifier field 410 identifies the network on the blacklist.Various ways to identify the network would be known to those in the art.For example, the identifier may be a subnet identifier for an EVDOnetwork or may be a Location Area Identifier, Absolute Radio FrequencyChannel Number (ARFCN), frequency band, Base Station Identity Code(BSIC), Public Land Mobile Network Identifier (PLMN ID), UTRA AbsoluteRadio Frequency Channel Number (UARFCN), Evolved Absolute RadioFrequency Channel Number (EARFCN), system identifier (SID), networkidentifier (NID), packet zone identifier (PZID) for other networks.Alternatively, an EVDO ColorCode may be utilized. The EVDO bandclass andchannel number, in addition to EVDO subnet identifier or EVDO ColorCode,can also be used in adding associated EVDO networks to the blacklist. Aswill be appreciated, in order to shrink the subnet identifier to asmaller value, ColorCodes may be assigned to EVDO networks such that theEVDO networks with the same ColorCode are geographically spaced apart toavoid conflicts.

Other identifiers that would identify the network may also be used inidentifier field 410.

In the example of FIG. 4, a timestamp field 420 may also be utilizedwith the identifier. In one embodiment, it is desirable that theblacklisting of a network be temporary. In other words, the blacklistedColorCode or identifier is not permanently placed on an avoidance list(blacklist). Temporary blacklisting provides for the possibility thaterror conditions may change in the future to allow access for the mobiledevice.

An example of such changes may be that roaming provisioning is grantedto the visiting mobile device at a later date. In this case, a suitabletimeout may be applied to automatically remove the ColorCode oridentifier from the blacklist. In this regard, timestamp 420 may beutilized to identify when the network was placed in the blacklist ofFIG. 4 (or alternatively the time the ColorCode or identifier should beremoved). This would allow the mobile to check for a time duration thatthe identifier of a network has been in the blacklist and to delete itwhen the predetermined threshold for the time has been exceeded.

For example, in FIG. 4, network identifier 1234 may have a firsttimestamp and network identifier 2345 may have a second timestamp. Ifnetwork identifier 1234 was placed into the blacklist first then thetimestamp for the network will show this and the expiration of thepredetermined time may be determined based on this timestamp. At thepredetermined time, identifier 1234 is removed from the blacklist whilenetwork identifier 2345 is maintained in the blacklist until expirationof that identifier.

As will appreciated by those in art, in alternative embodiments theblacklist may include only identifier field 410. In these embodiments,an alternative process to a timestamp may be utilized. For example, atimer may be started for each ColorCode or identifier or an interruptmay be set to cause the removal of the ColorCode or identifier. Otheroptions would be known to those in the art.

In other embodiments, the list may also be cleared when the mobiledevice turns its radio off. For example, the list may be cleared whenthe mobile device goes into an airplane mode, is powered off, or theradio is turned off manually, among other scenarios. In this case thelist may be cleared and when the radio is restored an attempt toestablish a data session over the blacklisted network may be made.

As will be appreciated, a user that expects provisioning changes to bemade may implement those provisioning changes on the mobile deviceimmediately by turning off and on the radio, rather than being requiredto wait for a timeout. Thus, if a user is expecting to be allowed to usea data session while roaming then the user could turn off the radio ofthe mobile device and then turn the radio back on. The resultingclearing of the blacklist of FIG. 4 will allow the data session to beestablished over the blacklisted network that has now been provisioned.

Reference is made to FIG. 5. FIG. 5 shows the clearing of the entries inthe blacklist of FIG. 4. The process of FIG. 5 starts at block 500 andproceeds to block 520 in which a check is made to determine whether datais expired in the blacklist. Such data is an identifier for a network ora ColorCode for an EVDO network.

If data has expired in the blacklist, the process proceeds from block520 to block 522 in which the expired data is cleared. As indicatedabove, the non-expired data is retained in the blacklist.

From block 522, the process proceeds back to block 520 to continue tocheck for expired data in the blacklist.

From block 520 if data has not expired in the blacklist, the processproceeds to block 530 in which a check is made to determine whether theradio has been turned off. If yes, then the process proceeds to block532 in which all data in the blacklist is cleared. From block 532 theprocess proceeds back to block 520 to continue to check whether data hasexpired in the blacklist.

In block 530 if the radio has not been turned off the process proceedsback to block 520 to continue to check for expiration of data in theblacklist.

FIGS. 2, 3, 4 and 5 provide for the establishment of a data session on asecond network if the first network is either on a blacklist or ifauthentication fails, which results in the network being placed on theblacklist. For example, if an EVDO network is on the blacklist or if ANauthentication fails, a data session is established on the related CDMA1× network. The establishment of the data session on the related CDMA 1×network rather than repeated attempts to establish an EVDO data sessionallows for the data establishment to occur more quickly, therebyenhancing user experience and saving battery and over the air resources.

Reference is now made to FIG. 6. FIG. 6 is a block diagram of anexemplary wireless data network in accordance with the presentdisclosure and with which the various embodiments of the methods of thepresent disclosure may cooperate. FIG. 6 shows a block diagram of awireless data device 610 and exemplary CDMA 1× network 620, an exemplaryEVDO network 630, a public switched telephone network (PSTN) 635, an IPnetwork 640, wireless gateway 642 and e-mail server 644. The wirelessdata device 610 is generally a two-way communication device having dataand voice communication capabilities.

CDMA network 620 includes a base transceiver station (BTS) 622 and abase station controller (BSC) 624. Base station controller 624communicates with a mobile switching centre 626 which as will beappreciated, is a circuit switched only component communicating withPSTN 635. Base station controller 624 further communicates with a packetdata serving node (PDSN) 628 which is a packet switched only component.PDSN 628 further communicates with IP network 640.

EVDO network 630 contains an EVDO sector 632, which communicates withaccess node (AN) 634. Since the EVDO network 630 is a data only network,access node 634 communicates only with PDSN 628 and not with any circuitswitched components.

An authentication, authorization and accounting node 636 is associatedwith AN 634, and a similar node 629 is associated with PDSN 628. OtherANs may (not shown) be communicated with through PDSN 628 and IP network640. Such other ANs will have associated AAA nodes.

Operationally, hybrid access terminal (mobile device) 610 communicateswirelessly with CDMA network 620 using BTS 622 and BSC 624 to gainaccess to the services provided by the CDMA 1× network. Depending on the1× and EVDO channel scanning sequences determined by the mobile deviceand the available 1× and EVDO networks over the air, in some cases CDMA1× network is acquired first and the establishment of the CDMA networkconnection occurs prior to any EVDO network connection beingestablished.

Mobile device 610 sends and receives both data and voice servicesthrough CDMA network 620 until an EVDO network connection isestablished. Base station controller 624 communicates with circuitswitch services provided by MSC 626 such as voice and short messageservice (SMS) via PSTN 635.

Prior to an EVDO connection being established, hybrid access terminal610 further communicates wirelessly with BTS 622 and BSC 624 to gainaccess to packet data services provided by PDSN 628, such as e-mail,wireless application protocol (WAP) and other data services via IPnetwork 640. Such services are provided through wireless gateway 642 andservers such as e-mail server 644.

Once a network connection is established with CDMA 1× network 620 andthe hybrid access terminal enters CDMA 1× idle state, wireless device610 may attempt to establish a connection with EVDO network 630. This isdone through EVDO sector 632 and AN 634. An authentication protocol asdescribed above with regards to FIG. 1 may be performed.

In this way, mobile device 610 may gain access to packet data servicesprovided by PDSN 628 using EVDO network 630. Subsequent to theestablishment of an EVDO network connection with mobile device 610, CDMAnetwork 620 is used to provide circuit switched services such as voiceand SMS while EVDO network 630 is used to provide packet data servicessuch as e-mail and WAP.

For the case when mobile device 610 acquires EVDO first, it may gainaccess to packet data services provided by PDSN 628 using EVDO network630. Once the hybrid access terminal enters EVDO idle state, the mobiledevice 610 may attempt to establish a connection with CDMA 1× network620 for circuit switch services provided by MSC 626 such as voice andshort message service (SMS) via PSTN 635.

As will be appreciated by those skilled in the art, mobile device 610can include voice communication means such as a headpiece 652 or a usercan communicate directly into the mobile device 610.

Mobile device 610 can also, in some cases, be used as a wireless modemand be connected through various means such as a USB or other serialport, or by short range wireless communications with a computer 654.Computer 654 can then gain access to IP network 640 through EVDO network630 using hybrid access terminal 610 as the modem.

As will be appreciated, the above can be implemented on any mobiledevice. One exemplary mobile device is described below with reference toFIG. 7. This is not meant to be limiting, but is provided forillustrative purposes.

FIG. 7 is a block diagram illustrating a mobile device capable of beingused with the embodiments of the apparatus and methods of the presentdisclosure. Mobile device 700 is typically a two-way wirelesscommunication device having voice communication capabilities. Dependingon the exact functionality provided, the mobile device may be referredto as a data messaging device, a two-way pager, a wireless e-maildevice, a cellular telephone with data messaging capabilities, awireless Internet appliance, a data communication device, a hybridaccess terminal, or a wireless device, as examples.

Where mobile device 700 is enabled for two-way communication, it willincorporate a communication subsystem 711, including both a receiver 712and a transmitter 714, as well as associated components such as one ormore, embedded or internal, antenna elements 716 and 718, localoscillators (LOs) 713, and a processing module such as a digital signalprocessor (DSP) 720. As will be apparent to those skilled in the fieldof communications, the particular design of the communication subsystem711 will be dependent upon the communication network in which the deviceis intended to operate.

Network access requirements will also vary depending upon the type ofnetwork 719. A mobile device may require a subscriber identity module(SIM) card or a removable user identity module (RUIM) in order tooperate on the network. The SIM/RUIM interface 744 is generally similarto a card-slot into which a SIM/RUIM card can be inserted and ejectedlike a diskette or PCMCIA card. The SIM/RUIM card may hold keyconfiguration 751, and other information 753 such as identification, andsubscriber related information.

When required network registration or activation procedures have beencompleted, mobile device 700 may send and receive communication signalsover the network 719. As illustrated in FIG. 7, network 719 can consistof multiple base stations communicating with the mobile device. Forexample, in a hybrid CDMA 1×/EVDO coverage, a CDMA base station and anEVDO base station communicate with the mobile device and the mobiledevice may be connected to both simultaneously. The EVDO and CDMA 1×base stations may use different paging slots to communicate with themobile device.

Signals received by antenna 716 through communication network 719 areinput to receiver 712, which may perform such common receiver functionsas signal amplification, frequency down conversion, filtering, channelselection and the like, and in the example system shown in FIG. 7,analog to digital (A/D) conversion. A/D conversion of a received signalallows more complex communication functions such as demodulation anddecoding to be performed in the DSP 720. In a similar manner, signals tobe transmitted are processed, including modulation and encoding forexample, by DSP 720 and input to transmitter 714 for digital to analogconversion, frequency up conversion, filtering, amplification andtransmission over the communication network 719 via antenna 718. DSP 720not only processes communication signals, but also provides for receiverand transmitter control. For example, the gains applied to communicationsignals in receiver 712 and transmitter 714 may be adaptively controlledthrough automatic gain control algorithms implemented in DSP 720.

Mobile device 700 generally includes a processor 738 which controls theoverall operation of the device. Communication functions, including dataand voice communications, are performed through communication subsystem711. Processor 738 also interacts with further device subsystems such asthe display 722, flash memory 724, random access memory (RAM) 726,auxiliary input/output (I/O) subsystems 728, serial port 730, one ormore keyboards or keypads 732, speaker 734, microphone 736, othercommunication subsystem 740 such as a short-range communicationssubsystem and any other device subsystems generally designated as 742.Serial port 730 could include a USB port or other port known to those inthe art.

Some of the subsystems shown in FIG. 7 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 732 and display722, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the processor 738 is generally storedin a persistent store such as flash memory 724, which may instead be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that the operating system, specificdevice applications, or parts thereof, may be temporarily loaded into avolatile memory such as RAM 726. Received communication signals may alsobe stored in RAM 726.

As shown, flash memory 724 can be segregated into different areas forboth computer programs 758 and program data storage 750, 752, 754 and756. These different storage types indicate that each program canallocate a portion of flash memory 724 for their own data storagerequirements. Processor 738, in addition to its operating systemfunctions, may enable execution of software applications on the mobiledevice. A predetermined set of applications that control basicoperations, including data and voice communication applications forexample, may typically be installed on mobile device 700 duringmanufacturing. Other applications could be installed subsequently ordynamically.

One software application may be a personal information manager (PIM)application having the ability to organize and manage data itemsrelating to the user of the mobile device such as, but not limited to,e-mail, calendar events, voice mails, appointments, and task items.Naturally, one or more memory stores could be available on the mobiledevice to facilitate storage of PIM data items. Such PIM applicationwould generally have the ability to send and receive data items, via thewireless network 719. In one embodiment, the PIM data items areseamlessly integrated, synchronized and updated, via the wirelessnetwork 719, with the mobile device user's corresponding data itemsstored or associated with a host computer system. Further applicationsmay also be loaded onto the mobile device 700 through the network 719,an auxiliary I/O subsystem 728, serial port 730, short-rangecommunications subsystem 740 or any other suitable subsystem 742, andinstalled by a user in the RAM 726 or a non-volatile store (not shown)for execution by the processor 738. Such flexibility in applicationinstallation increases the functionality of the device and may provideenhanced on-device functions, communication-related functions, or both.For example, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing the mobile device 700.

In a data communication mode, a received signal such as a text messageor web page download may be processed by the communication subsystem 711and input to the processor 738, which may further process the receivedsignal for element attributes for output to the display 722, oralternatively to an auxiliary I/O device 728.

A user of mobile device 700 may also compose data items such as emailmessages for example, using the keyboard 732, which is, in oneembodiment, a complete alphanumeric keyboard or telephone-type keypad,in conjunction with the display 722 and possibly an auxiliary I/O device728. Such composed items may then be transmitted over a communicationnetwork through the communication subsystem 711.

For voice communications, overall operation of mobile device 700 issimilar, except that received signals could be output to a speaker 734and signals for transmission could be generated by a microphone 736.Alternative voice or audio I/O subsystems, such as a voice messagerecording subsystem, may also be implemented on mobile device 700.Although voice or audio signal output is accomplished generally throughthe speaker 734, display 722 may also be used to provide an indicationof the identity of a calling party, the duration of a voice call, orother voice call related information for example.

Serial port 730 in FIG. 7 could be implemented in a personal digitalassistant (PDA)-type mobile device for which synchronization with auser's desktop computer (not shown) may be desirable, but is an optionaldevice component. Such a port 730 would enable a user to set preferencesthrough an external device or software application and would extend thecapabilities of mobile device 700 by providing for information orsoftware downloads to mobile device 700 other than through a wirelesscommunication network. The alternate download path may for example beused to load an encryption key onto the device through a direct and thusreliable and trusted connection to thereby enable secure devicecommunication. As will be appreciated by those skilled in the art,serial port 730 can further be used to connect the mobile device to acomputer to act as a modem.

Other communications subsystems 740, such as a short-rangecommunications subsystem, is a further component which may provide forcommunication between mobile device 700 and different systems ordevices, which need not necessarily be similar devices. For example, thesubsystem 740 may include an infrared device and associated circuits andcomponents or a Bluetooth™ communication module to provide forcommunication with similarly enabled systems and devices. Subsystem 740may also be used for WiFi or WiMAX communications.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis application. This written description may enable those skilled inthe art to make and use embodiments having alternative elements thatlikewise correspond to the elements of the techniques of thisapplication. The intended scope of the techniques of this applicationthus includes other structures, systems or methods that do not differfrom the techniques of this application as described herein, and furtherincludes other structures, systems or methods with insubstantialdifferences from the techniques of this application as described herein.

1-20. (canceled)
 21. A method for data session establishment from amobile device comprising: checking whether an identifier for a firstnetwork is on a blacklist on the mobile device; if the first networkidentifier is not on the blacklist, attempting to establish a dataconnection with the first network, said attempting comprising performingauthentication with an authentication entity of the first network; ifthe attempt to establish the data connection is unsuccessful, adding thefirst network identifier and identifiers of associated networks to theblacklist, the associated networks having a common authentication entitywith the first network; and if the first network identifier is on theblacklist, establishing a data connection with a second network having adifferent authentication entity, wherein the first network andassociated networks are associated based on information stored on themobile device.
 22. The method of claim 21, wherein the first network isa higher data throughput Radio Access Technology than the secondnetwork.
 23. The method of claim 21, wherein the first network is anEvolution Data Only (EVDO) network and the second network is a CodeDivision Multiple Access (CDMA) 1× network.
 24. The method of claim 23,further comprising adding the EVDO network identifier to the blacklistif the attempt to establish a data connection is unsuccessful.
 25. Themethod of claim 24, wherein a data connection is established with theCDMA network subsequent to the addition of the EVDO network identifierto the blacklist.
 26. The method of claim 24, wherein the attempting toestablish performs an access network (AN) authentication and wherein theattempting to establish is unsuccessful if the AN authentication returnsa rejection.
 27. The method of claim 24, wherein the adding the EVDOnetwork identifier further comprises adding EVDO network identifiers forEVDO networks associated with a current EVDO network to the blacklist.28. The method of claim 21, wherein the first network identifier is atleast one of an EVDO ColorCode, an EVDO subnet identifier, an EVDObandclass, an EVDO channel number, a Location Area Identifier, anAbsolute Radio Frequency Channel Number (ARFCN), a frequency band, aBase Station Identity Code (BSIC), a Public Land Mobile NetworkIdentifier (PLMN ID), an UTRA Absolute Radio Frequency Channel Number(UARFCN), an Evolved Absolute Radio Frequency Channel Number (EARFCN), asystem identifier (SID), a network identifier (NID) or a packet zoneidentifier (PZID).
 29. The method of claim 21, wherein the blacklistfurther contains a time value associated with the first networkidentifier, said time value being utilized for the expiration of thefirst network identifier on the blacklist.
 30. The method of claim 21,further comprising checking whether a radio of the mobile device hasbeen turned off, and if the radio has been turned off clearing theblacklist of all entries.
 31. The method of claim 21, wherein theinformation stored on the mobile device is received in a broadcastmessage and stored on the mobile device, or wherein the informationstored on the mobile device is provisioned onto the mobile device.
 32. Amobile device configured for data session establishment with a networkcomprising: a communications subsystem; and a processor, wherein themobile device is configured to: check whether an identifier for a firstnetwork is on a blacklist on the mobile device; if the first networkidentifier is not on the blacklist, attempt to establish a dataconnection with the first network, the attempt comprising performingauthentication with an authentication entity of the first network; ifthe attempt to establish the data connection is unsuccessful, add thefirst network identifier and identifiers of associated networks to theblacklist, the associated networks having a common authentication entitywith the first network; and if the first network identifier is on theblacklist, establishing a data connection with a second network having adifferent authentication entity, wherein the first network andassociated networks are associated based on information stored on themobile device.
 33. The mobile device of claim 32, wherein the firstnetwork is a higher data throughput Radio Access Technology than thesecond network.
 34. The mobile device of claim 32, wherein the firstnetwork has a smaller footprint than the second network.
 35. The mobiledevice of claim 32, wherein the first network is an Evolution Data Only(EVDO) network and the second network is a Code Division Multiple Access(CDMA) network.
 36. The mobile device of claim 35, further configured toadd the EVDO network identifier to the blacklist if the attempt toestablish a data connection is unsuccessful.
 37. The mobile device ofclaim 36, wherein a data connection is established with the CDMA networksubsequent to the addition of the EVDO network identifier to theblacklist.
 38. The mobile device of claim 37, wherein the adding theEVDO network identifier includes adding EVDO network identifiers forEVDO networks associated with a current EVDO network to the blacklist.39. The mobile device of claim 32, wherein the information stored on themobile device is received in a broadcast message and stored on themobile device, or wherein the information stored on the mobile device isprovisioned onto the mobile device.
 40. A non-transitorycomputer-readable medium having executable code stored thereon forexecution by a processor of a mobile device, the executable codecomprising instructions for: checking whether an identifier for a firstnetwork is on a blacklist on the mobile device; if the first networkidentifier is not on the blacklist, attempting to establish a dataconnection with the first network, said attempting comprising performingauthentication with an authentication entity of the first network; ifthe attempt to establish the data connection is unsuccessful, adding thefirst network identifier and identifiers of associated networks to theblacklist, the associated networks having a common authentication entitywith the first network; and if the first network identifier is on theblacklist, establishing a data connection with a second network having adifferent authentication entity, wherein the first network andassociated networks are associated based on information stored on themobile device.